home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.c
- Subject: Re: malloc question
- Date: 11 Mar 1996 11:26:11 -0800
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4i1uojINN4gl@keats.ugrad.cs.ubc.ca>
- References: <4htonk$350@news.hklink.net> <4huctt$arv@sparcserver.lrz-muenchen.de> <4hv5qpINNp8a@keats.ugrad.cs.ubc.ca> <AD69AACC9668D7849@mcdiala09.it.luc.edu>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <AD69AACC9668D7849@mcdiala09.it.luc.edu>,
- Verne Arase <VArase@varase.it.luc.edu> wrote:
- >In article <4hv5qpINNp8a@keats.ugrad.cs.ubc.ca>,
- >c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku) wrote:
- >
- >>A C compiler is free to treat it, and other defined functions, as a
- >>special operator for the purposes of optimizing a call to malloc(),
- >>unless it has already encountered a static declaration of the malloc
- >>identifier in the scope where the call occurs---malloc() is no mere
- >>external function, it is a special language feature painstakingly
- >>dressed up to look like a library function, even to the point that
- >>you can take the address of malloc() and call it via a function
- >>pointer.
- >
- >Not malloc(); malloc. malloc() is an invocation.
-
- The above is english not C. Why not just say that "address of malloc()" is
- a parse error and be done with it?
-
-
- --
-
-